Patch esbuild advisory (GHSA-gv7w-rqvm-qjhr) + add SDK-moved README notice#120
Merged
Merged
Conversation
Dependabot flagged esbuild GHSA-gv7w-rqvm-qjhr (high) via the dev-only tsx dependency in examples/. Bump tsx ^4.19.2 -> ^4.22.4 so esbuild resolves to the patched 0.28.1. No change to the published package. Also add an [!IMPORTANT] banner pointing to the new SDK home at github.com/opper-ai/opper-sdks. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
tsx^4.19.2→^4.22.4inexamples/, which resolves the transitiveesbuilddependency to 0.28.1 — the patched version for GHSA-gv7w-rqvm-qjhr (High, CVSS 8.1).[!IMPORTANT]banner to the README noting the SDKs have moved to https://github.com/opper-ai/opper-sdks.Risk context
esbuild was a dev-only, transitive dependency, present only in
examples/package-lock.json(aprivateworkspace) — it is not part of the publishedopperainpm package. The advisory itself only affects esbuild's Deno install path (binary download without integrity verification, redirectable viaNPM_CONFIG_REGISTRY); the examples run esbuild through tsx on Node, so the vulnerable code path was never exercised here. Low practical risk, but this clears the alert.Verification
npm ls esbuild→tsx@4.22.4 → esbuild@0.28.1✅npm audit→ 0 vulnerabilities ✅npx tsx -e ...runs fine — examples toolchain unaffected ✅Publishing
No security republish to npm is required — nothing in the published package changed. (Optional:
npm deprecate opperai "Moved to https://github.com/opper-ai/opper-sdks"if we want the move reflected on the npm page.)🤖 Generated with Claude Code